home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Grab Bag
/
Shareware Grab Bag.iso
/
095
/
pcb90upd.arc
/
README.90!
Wrap
Text File
|
1985-12-22
|
12KB
|
238 lines
***** New Features in version 9.0 Beta - 12/22/85 *****
Version 9.0 of PCBoard is a major enhancement of previous issues and
makes it one of the most flexible BBS programs available. It now
offers more features and functions than before - including the most
comprehensive message reading capability of any BBS communications
program in the industry. Additionally, it now allows for the importing
of message files into the code in an interative manner. We think you
will enjoy the new features of code! If you agree with us that this
version of PCBoard is one of the best BBS programs available - we
would appreciate your support in our continuing efforts of bringing
you the best software around by asking for your donation to support
our programming efforts. If you would like to donate to the cause,
you can forward your donation to:
Fred Clark
P.O. Box 71365
Muray, UT 84107
Remember - all folks who help out with this effort with a donation
also get access to the Salt Air Board at (801) 266-0328!
1. Fixes a bug which could cause the message pointers inside a
conference to get messed up. This occurred if the sysop pressed
a function key while the caller was reading a message. This
was most likely also a problem in pre v 9.0 code as well. If
you are running any version of PCBoard code - it is recommended
that you DO NOT press any function keys while the caller is inside
a conference reading messages. The new code provides for almost
immediate response to any function key pressed.
2. Revised message "Status" to show the word "Sec'ty" for security
and the following qualifiers:
Public Message
Receiver Only
Group Password (Old 'Password' status)
Sender Password (Old 'Kill' status)
3. Included either the words "Main Board" or "xxxxxx Conference"
in front of "Bulletin # 1 read." message which is written to
the caller's log to assist call analyzer programs.
4. The ability to read [N]ext and [P]revious messages has been
added to the main Message Base Command Line. If a caller reads
one message, and then is returned to the "Msg(s) [1 - xx]"
command line, they can read the next message in line by just
entering an [N] for next. Or they can read the previous on
by entering a [P] for previous. If they have not read a message
and enter the [N] command, reading will start at the first active
message. If they enter a [P], the main menu will be redisplayed.
5. If the caller now just enters a "+" or "-" at the message read
"More: " prompt, the code will recognize the request and begin
processing forward or backwards - without the need of inputting
a corresponding message number.
6. If message read "Help" is requested, the caller will be returned
to the Message Command Line rather than the Main Menu Command
line as presently happens.
7. The board will now run an automatic date check of the current date
of the respective BLT file and indicate to the caller whether the
file has been updated since their last call. This display will
be shown them just before the message "Do you want to check your
mail" when entering the main board, and just before the "View
other conference members" when joining a conference. In each
case, the board will check the date of the BLT file that
corresponds to the area of the board the caller is in. This is
done through an assembly language routine provided by David Terry.
If the file's DOS date stamp is LATER than the caller's last date
on the system, they will be shown the message "Bulletins have
been updated since your last call ..." If the date is equal to or
less than the caller's last date on the system, they will not be
shown the above message. In other words, to have the message
appear, you must have physically gone into the BLT file and updated
it so that it's DOS date stamp is altered. Please note that only
the BLT and xBLT files are checked - not the graphics versions -
irregardless of whether the caller is in graphics mode or not.
8. The code no longer places the "[R]" in the subject matter of a
message if it is a message which is a reply to another message.
Because of the new message header display - this is no longer
needed. Be aware that because of this change, [T]hread reading
may be off on those messages which are a combination of both
types of subject display.
9. The code uses an intelligent message header format to better
display message status and received information.
10. Provides for better paper handling capability when used with
the HP Laserjet or equivalent printer engine.
11. Fixes a bug where the board did not properly set a flag on
returning to the system from remote DOS. This would then cause
a problem if a function key was pressed at the local terminal.
The problem was that the board thought it was waiting for a
call instead of actually inside the code and the function keys
would respond accordingly.
12. The board now uses a highly modified method of mail read/quick
scan functions. The heart of the new command procedure is a
routine which "scans" the user's requests and attempts to
process those requests - irreguardless of the order in which
they are entered. The basic command structure to read or
scan messages is comprised of three main commands:
A: [R] for read
B: [S] for since last message # read (old "*" command)
C: [Y] for mail addressed to you
D: [F] for mail from you
E: [N] for next message
F: [P] for previous message
Here are some examples:
R S [R]ead all new mail [S]ince you last logged on (just like
R;* which also still works).
R Y [R]ead [Y]our mail, that is, all mail addressed to you.
R S Y Read all new mail addressed to you.
R Y S Same thing -- the order doesn't count.
R Y 250 Read all mail addressed to you higher than number 250.
R 250 Y Same thing.
R F [R]ead all mail [F]rom you to others (you can check to
see if a message has been received and/or kill it if
it has become outdated).
R F 250 Read mail from you to others higher than number 250.
R 250 F Same thing.
R F Y Read all mail from or to you.
R F Y 250 Read mail from or to you higher than number 250.
Other combinations of [R] and its subcommands will work as well.
PCBoard will intelligently parse any combination, and return an
appropriate "error" message if it finds nothing to read in response
to your request.
You can stack the commands, as shown above, or give them in response
to the system's prompts. You can even use the "old" method of
separating the commands with semi-colons, e.g. R;S;Y , but I find
that spaces instead of semi's are easier and PCBoard allows it.
All the same commands work with Q)uick Msg Scan as well.
Please note that the [*] command will still function as normal -
just like the new [S]ince command. However, the [*] prompt
will no longer be displayed - since many new callers to most
BBS systems had no idea what the [*] meant!
13. The board uses a slightly modified message display header.
It now displays the message date, who the message is to, who the
message is from and the subject on the left side of the screen.
The message number, reference message number, whether the message
has been read by the receiver, and the message security level
on the right side of the screen. If the reference message number
is lower than the lowest active message number in that message
base - the reference number will show "none". This was done to
prevent callers from trying to read a message which was no longer
available.
14. The code will now ask you to verify whether or not to actually
delete the caller's log if you enter a [2] followed by [D].
Seems there were a few caller's logs accidentally deleted
because of the confusion between the [D]isplay command used
to display comments, and the [D]elete command used to delete
the caller's log.
15. The sysop function keys are now activated almost immediately
at all times. If it is necesary to write the new change to the
message base header, the status is "saved" until the caller
logs off or the system exits to DOS.
16. The code will now recognize a stacked protocol command at the
"Enter the full filename to upload/download" - in case the
user forgot to stack it at the main command line.
17. The program now supports messages up to 60 lines long. This can
be set by the sysop in the PCBSETUP program.
18. The code now provides for screen pauses when listing messages
greater than the page length specified when entering a message
and requesting the [L]ist option.
19. The code now places a blank line between the last message line and
the "More: [Y]es, [N]o, [NS]non-stop, [#], [T]hread, [RE]ply"
command. It also inserts a blank line between the last file
directory/bulletin listing and the "Directories (1 - xx)"
prompt.
20. The code now allows for importing a message into the message
base from local mode when typing in a message as the sysop.
The file must be an ascii file - properly pre-configured - which
will be inserted into the message as if it were typed at the
keyboard. Several messages or parts thereof can be inserted
into one message. Paths and error trapping is provided for
this function.
21. If the sysop's screen display if off and a page is responded to,
the program now first resets the display back to 'on' before
continuing with chat mode.
22. The sysop can now specify the intensity and color of the caller's
and keyboard input. This will allow tailoring of the system to
better match the system's needs. Also, the non-graphics colors
are also handled better than was previously done.
23. In order to facilitate a call analyzer program, the code will
write to a separate file the name, transfer protocol, and
total errors of all files downloaded. This information is
written to a file called DOWNLOAD.TXT which is created in the
'\MAIN' subdirectory. Entries in the file will appear as:
--------------------------------------
PCBRD82.ARC,C, 0
NEWS,A, 0
PCBRD82.ARC,Y, 0
--------------------------------------
etc. By not having to scan the entire caller's log for download
information, a much simplified file download analyzer program
should be able to be written by those sysops interested in doing
so. Only completed downloads are recorded here.
24. The board will now recycle after 60 seconds at the "Do you want
color graphics" prompt if the caller fails to enter anything
at that point.
25. The sysop - either in local or remote mode can no longer enter
a TAB. This has been messing up the files and is no longer a
valid key to use in the code.